SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Service Component Architecture</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Service Component Architecture</span></span>

</h1>

</header>

<p><b>Service Component Architecture</b> (<b>SCA</b>) is a software technology designed to provide a model for applications that follow <a href="Service-oriented_architecture" title="Service-oriented architecture">service-oriented architecture</a> principles.<sup id="cite_ref-OASIS_1-0" class="reference"><a href="#cite_note-OASIS-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> The technology, created by major software vendors, including <a href="IBM" title="IBM">IBM</a>, <a href="Oracle_Corporation" title="Oracle Corporation">Oracle Corporation</a> and <a href="TIBCO_Software" title="TIBCO Software">TIBCO Software</a>, encompasses a wide range of technologies and as such is specified in independent specifications to maintain programming language and application environment neutrality.<sup id="cite_ref-OASIS_1-1" class="reference"><a href="#cite_note-OASIS-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> Many times it uses an <a href="Enterprise_service_bus" title="Enterprise service bus">enterprise service bus</a> (ESB).

</p>

<div class="mw-heading mw-heading2"><h2 id="History">History</h2></div>

<p>The original partners announced on November 30, 2005 were: <a href="BEA_Systems" title="BEA Systems">BEA Systems</a>, <a href="IBM" title="IBM">IBM</a>, <a href="IONA_Technologies" title="IONA Technologies">IONA Technologies</a>, <a href="Oracle_Corporation" title="Oracle Corporation">Oracle Corporation</a>, <a href="SAP_AG" class="mw-redirect" title="SAP AG">SAP AG</a>, <a href="Sybase" title="Sybase">Sybase</a>, Xcalia and <a href="Zend_Technologies" class="mw-redirect" title="Zend Technologies">Zend Technologies</a>.<sup id="cite_ref-gartner2005_2-0" class="reference"><a href="#cite_note-gartner2005-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup>

Additional members announced on July 26, 2006 were <a href="Cape_Clear_(software_company)" class="mw-redirect" title="Cape Clear (software company)">Cape Clear</a>, <a href="Interface21" class="mw-redirect" title="Interface21">Interface21</a>, Primeton Technologies, <a href="Progress_Software" title="Progress Software">Progress Software</a>, <a href="Red_Hat" title="Red Hat">Red Hat</a>, <a href="Rogue_Wave_Software" title="Rogue Wave Software">Rogue Wave Software</a>, <a href="Software_AG" title="Software AG">Software AG</a>, <a href="Sun_Microsystems" title="Sun Microsystems">Sun Microsystems</a> and <a href="TIBCO_Software" title="TIBCO Software">TIBCO Software</a>.<sup id="cite_ref-3" class="reference"><a href="#cite_note-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup>

<a href="Siemens_AG" class="mw-redirect" title="Siemens AG">Siemens AG</a> joined the collaboration of companies working on the technology on September 18, 2006.

</p><p>In addition to the partners, the SCA community had some formal supporters.<sup id="cite_ref-4" class="reference"><a href="#cite_note-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="Definition">Definition</h2></div>

<p>On March 21, 2007, the OSOA Collaboration released the first version of specification.<sup id="cite_ref-5" class="reference"><a href="#cite_note-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup>

The specifications said that an application designed with SCA should have:

</p>

<ul><li>Decoupling of application business logic from the details of its invoked service calls</li>

<li>Target services in a multitude of languages including <a href="C%2B%2B" title="C++">C++</a>, <a href="Java_(programming_language)" title="Java (programming language)">Java</a>, <a href="COBOL" title="COBOL">COBOL</a>, and <a href="PHP" title="PHP">PHP</a> as well as <a href="XML" title="XML">XML</a>, <a href="BPEL" class="mw-redirect" title="BPEL">BPEL</a>, and <a href="XSLT" title="XSLT">XSLT</a></li>

<li>The ability to work with various communications constructs including one-way, asynchronous, call-return, and notification</li>

<li>The ability to "bind" to legacy components or services, accessed normally by technologies such as <a href="Web_Services" class="mw-redirect" title="Web Services">Web Services</a>, <a href="Enterprise_JavaBean" class="mw-redirect" title="Enterprise JavaBean">EJB</a>, <a href="Java_Message_Service" class="mw-redirect" title="Java Message Service">JMS</a>, <a href="Java_EE_Connector_Architecture" class="mw-redirect" title="Java EE Connector Architecture">JCA</a>, <a href="Java_remote_method_invocation" title="Java remote method invocation">RMI</a>, <a href="Remote_procedure_call" title="Remote procedure call">RPC</a>, <a href="CORBA" class="mw-redirect" title="CORBA">CORBA</a> and others</li>

<li>The ability to declare (outside of business logic) the <a href="Quality_of_service" title="Quality of service">quality of service</a> requirements, such as security, transactions and the use of reliable messaging</li>

<li>Data could be represented in <a href="Service_Data_Objects" title="Service Data Objects">Service Data Objects</a></li></ul>

<p>SCA, therefore, was promoted to offer flexibility for <a href="Composite_applications" class="mw-redirect" title="Composite applications">composite applications</a>, flexibly incorporating reusable components in an SOA programming style.

</p><p>Marketing firm <a href="Gartner_Group" class="mw-redirect" title="Gartner Group">Gartner Group</a> published a short brief that promoted the SCA and its included technology of <a href="Service_Data_Objects" title="Service Data Objects">Service Data Objects</a> (SDO) in December 2005 .<sup id="cite_ref-gartner2005_2-1" class="reference"><a href="#cite_note-gartner2005-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup>

</p><p>Advantages:

</p>

<ul><li>caters for all existing <a href="Java_platform" class="mw-redirect" title="Java platform">Java platform</a> technologies and C++</li>

<li>less technology dependence – does not have to rely on the <a href="Java_(programming_language)" title="Java (programming language)">Java programming language</a> or <a href="XML" title="XML">XML</a></li>

<li><a href="Service_Data_Objects" title="Service Data Objects">Service Data Objects</a> is a technology specification for data access</li></ul>

<p>Disadvantages:

</p>

<ul><li>Specification does not address performance of SOA applications, which continues to be a detractor of adoption.</li>

<li>Focusing on portability (instead of interoperability),<sup id="cite_ref-6" class="reference"><a href="#cite_note-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup> making it vulnerable to repeating <a href="CORBA" class="mw-redirect" title="CORBA">CORBA</a>'s mistakes.<sup id="cite_ref-7" class="reference"><a href="#cite_note-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup></li></ul>

<p>SCA was said to provide interoperability through an approach called "Activation". It is the method that provides the highest degree of component autonomy, compared to older "mediation" (e.g., <a href="Java_Business_Integration" title="Java Business Integration">JBI</a>) or "Invocation" method used in <a href="J2EE_Connector_Architecture" class="mw-redirect" title="J2EE Connector Architecture">JCA</a>, as explained by an architect at SAP.<sup id="cite_ref-8" class="reference"><a href="#cite_note-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="Artifacts">Artifacts</h2></div>

<p>The <b>SCA Assembly Model</b> consists of a series of artifacts, which are defined by elements contained in XML files. An SCA runtime may have other non-standard representations of the artifacts represented by these XML files, and may allow for the configuration of systems to be modified dynamically. However, the XML files define the portable representation of the SCA artifacts.

</p><p>The basic artifact is the <b>composite</b>, which is the unit of deployment for SCA and which holds <b>services</b> that can be accessed remotely. A composite contains one or more <b>components</b>,<sup id="cite_ref-9" class="reference"><a href="#cite_note-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup> which contain the business function provided by the module. Components offer their function as services, which can either be used by other components within the same module or which can be made available for use outside the module through <b>Entry Points</b>. Components may also depend on services provided by other components — these dependencies are called <b>references</b>. References can either be linked to services provided by other components in the same module, or references can be linked to services provided outside the module, which can be provided by other modules. References to services provided outside the module, including services provided by other modules, are defined by External Services in the module. Also contained in the module are the linkages between references and services, represented by <b>wires</b>.

</p><p>A component consists of a configured <b>implementation</b>, where an implementation is the piece of program code implementing business functions. The component configures the implementation with specific values for settable <b>properties</b> declared by the implementation. The component can also configure the implementation with wiring of references declared by the implementation to specific target services.

</p><p>Composites are deployed within an <b>SCA System</b>. An SCA System represents a set of services providing an area of business functionality that is controlled by a single organization. As an example, for the accounts department in a business, the SCA System might cover all financial-related functions, and it might contain a series of modules dealing with specific areas of accounting, with one for customer accounts and another dealing with accounts payable. To help build and configure the SCA System, Composites can be used as component implementations, in the same way as Java classes or <a href="Business_Process_Execution_Language" title="Business Process Execution Language">BPEL</a> processes. In other words, SCA allows a hierarchy of composites that is arbitrarily deep – such a nested model is termed recursive.

</p><p>The capture and expression of non-functional requirements, such as security, is an important aspect of service definition, and affects SCA throughout the life-cycle of components and compositions. SCA provides the <b>Policy Framework</b> to support specification of constraints, capabilities and Quality of Service (QoS) expectations, from component design through to concrete deployment.

</p>

<div class="mw-heading mw-heading2"><h2 id="Transition_to_a_standards_body">Transition to a standards body</h2></div>

<p>After several years of incubation under an informal industry collaboration, early (V1.0) implementations of the specification are now coming to market. The collaboration partners indicated that formal industry standardization would be the appropriate next step and announced their intentions in March 2007. The chosen Standards Development Organization is the <a href="OASIS_(organization)" title="OASIS (organization)">OASIS organization</a>, and a new <a href="OASIS_(organization)" title="OASIS (organization)">OASIS</a> <a rel="nofollow" class="external text" href="http://www.oasis-opencsa.org">Open CSA</a> Member Section has been established.<sup id="cite_ref-10" class="reference"><a href="#cite_note-10"><span class="cite-bracket">[</span>10<span class="cite-bracket">]</span></a></sup> Charters for six new Technical Committees (TCs) have been submitted to OASIS<sup id="cite_ref-11" class="reference"><a href="#cite_note-11"><span class="cite-bracket">[</span>11<span class="cite-bracket">]</span></a></sup> and a Call for Participation for Technical Committee members has been issued within the OASIS organization. The Technical Committees planned to start their work in September 2007. Participation in these OASIS SCA TCs remains open to all companies, non-profit groups, governments, academic institutions, and individuals. Archives of the work will be accessible to both members and non-members, and OASIS will offer a mechanism for public comment.<sup id="cite_ref-12" class="reference"><a href="#cite_note-12"><span class="cite-bracket">[</span>12<span class="cite-bracket">]</span></a></sup>

</p>

<ul><li>Apache ServiceMix</li>

<li><a href="Business_Process_Model_and_Notation" title="Business Process Model and Notation">Business Process Model and Notation</a> (BPMN)</li>

<li><a href="Docker_(software)" title="Docker (software)">Docker (software)</a></li>

<li><a href="Enterprise_application_integration" title="Enterprise application integration">Enterprise application integration</a> (EAI)</li>

<li><a href="Mule_(software)" title="Mule (software)">Mule (software)</a></li>

<li><a href="Reactive_programming" title="Reactive programming">Reactive programming</a></li>

<li><a href="Semantic_service-oriented_architecture" title="Semantic service-oriented architecture">Semantic service-oriented architecture</a> (SSOA)</li>

<li><a href="Service-oriented_modeling" title="Service-oriented modeling">Service-oriented modeling</a></li>

<li><a href="Windows_Communication_Foundation" title="Windows Communication Foundation">Windows Communication Foundation</a> (WCF)</li></ul>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite id="CITEREFEdwards" class="citation web cs1">Edwards, Mike. <a rel="nofollow" class="external text" href="http://oasis-opencsa.org/sca">"Service Component Architecture"</a>. OASIS<span class="reference-accessdate">. Retrieved <span class="nowrap">7 April</span> 2011</span>.</cite></span>

</li>

<li id="cite_note-gartner2005-2"><span class="mw-cite-backlink">^ <a href="#cite_ref-gartner2005_2-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-gartner2005_2-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><cite id="CITEREFDaniel_ShollerDavid_Mitchell_Smith2005" class="citation web cs1">Daniel Sholler; David Mitchell Smith (December 5, 2005). <a rel="nofollow" class="external text" href="http://www.gartner.com/resources/136600/136687/new_soa_specification_will_f_136687.pdf">"New SOA Specification Will Fill Niche Among Java Users"</a> <span class="cs1-format">(PDF)</span>. Gartner Group<span class="reference-accessdate">. Retrieved <span class="nowrap">April 29,</span> 2017</span>.</cite></span>

</li>

<li id="cite_note-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-3">^</a></b></span> <span class="reference-text">Technology srinivas vendors extend collaboration on SOA technologies <a rel="nofollow" class="external free" href="http://www.hoise.com/primeur/06/articles/monthly/AE-PR-08-06-92.html">http://www.hoise.com/primeur/06/articles/monthly/AE-PR-08-06-92.html</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20110712213641/http://www.hoise.com/primeur/06/articles/monthly/AE-PR-08-06-92.html">Archived</a> 2011-07-12 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a></span>

</li>

<li id="cite_note-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-4">^</a></b></span> <span class="reference-text">OSOA Technology Supporters <a rel="nofollow" class="external free" href="http://www.osoa.org/display/Main/Current+OSOA+Supporters+Community">http://www.osoa.org/display/Main/Current+OSOA+Supporters+Community</a></span>

</li>

<li id="cite_note-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-5">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20071012184346/http://osoa.org/display/Main/Service+Component+Architecture+Specifications">"Service Component Architecture Specifications"</a>. <i>Open SOA Collaboration web site</i>. Archived from <a rel="nofollow" class="external text" href="http://www.osoa.org/display/Main/Service+Component+Architecture+Specifications">the original</a> on October 12, 2007<span class="reference-accessdate">. Retrieved <span class="nowrap">April 29,</span> 2017</span>.</cite></span>

</li>

<li id="cite_note-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-6">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external autonumber" href="http://blogs.ittoolbox.com/eai/applications/archives/sca-sdo-the-next-corba-10836">[1]</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20080705043109/http://blogs.ittoolbox.com/eai/applications/archives/sca-sdo-the-next-corba-10836">Archived</a> 2008-07-05 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a> SCA & SDO, the next Corba?</span>

</li>

<li id="cite_note-7"><span class="mw-cite-backlink"><b><a href="#cite_ref-7">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20081202033636/http://www.acmqueue.com/modules.php?name=Content&pa=showpage&pid=396">"ACM Queue - the Rise and Fall of CORBA: The story behind this once-promising distributed computing technology-why it fell short, and what we can learn from it"</a>. Archived from <a rel="nofollow" class="external text" href="http://www.acmqueue.com/modules.php?name=Content&pa=showpage&pid=396">the original</a> on 2008-12-02<span class="reference-accessdate">. Retrieved <span class="nowrap">2011-04-08</span></span>.</cite> The rise and fall of CORBA</span>

</li>

<li id="cite_note-8"><span class="mw-cite-backlink"><b><a href="#cite_ref-8">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://archive.today/20121217172144/https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2824">"community.user: Comparing SCA, Java EE and JBI | SCN"</a>. Sdn.sap.com. 2005-12-12. Archived from <a rel="nofollow" class="external text" href="https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2824">the original</a> on 2012-12-17<span class="reference-accessdate">. Retrieved <span class="nowrap">2013-06-16</span></span>.</cite></span>

</li>

<li id="cite_note-9"><span class="mw-cite-backlink"><b><a href="#cite_ref-9">^</a></b></span> <span class="reference-text"><cite id="CITEREFBell2008" class="citation book cs1">Bell, Michael (2008). <a rel="nofollow" class="external text" href="http://www.wiley.com/WileyCDA/WileyTitle/productCd-0470141115.html">"Service-Oriented Conceptualization"</a>. <i>Service-Oriented Modeling: Service Analysis, Design, and Architecture</i>. Wiley & Sons. p. 3. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-470-14111-3</bdi>.</cite></span>

</li>

<li id="cite_note-10"><span class="mw-cite-backlink"><b><a href="#cite_ref-10">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.oasis-opencsa.org/sca">"OASIS Open CSA Member Section for SCA"</a>.</cite></span>

</li>

<li id="cite_note-11"><span class="mw-cite-backlink"><b><a href="#cite_ref-11">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://xml.coverpages.org/ni2007-07-06-a.html">"Six Technical Committees Proposed for the OASIS Open CSA Member Section"</a>.</cite></span>

</li>

<li id="cite_note-12"><span class="mw-cite-backlink"><b><a href="#cite_ref-12">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.oasis-open.org/news/oasis-news-2007-08-09.php">"Six OASIS Committees Form to Standardize Service Component Architecture (SCA) for SOA"</a>.</cite></span>

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="Further_reading">Further reading</h2></div>

<ul><li>Understanding SCA from experts Jim Marino and Michael Rowley <a rel="nofollow" class="external autonumber" href="http://my.safaribooksonline.com/9780321617927">[2]</a></li>

<li>SOA for the Business Developer: Concepts, BPEL, and SCA—<a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-158347-065-7</bdi></li>

<li>Apache Tuscany in Action, <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-933988-89-4</bdi></li>

<li>Open Source SOA, <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>1-933988-54-1</bdi></li></ul>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

<ul><li><a rel="nofollow" class="external text" href="https://lists.oasis-open.org/archives/sca-assembly-comment/201302/msg00000.html">Mail of 2013-02-19 with Death of OASIS SCA Assembly technical committee, on that mail the amazing SCA died</a></li>

<li><a rel="nofollow" class="external text" href="https://lists.oasis-open.org/archives/sca-assembly-comment/201502/msg00000.html">Mail of 2015-02-20 with the leader Jim Marino telling about Oracle killing SCA</a></li>

<li><a rel="nofollow" class="external text" href="https://soa.netbeans.org/">NetBeans SOA Composite Application Project Home</a></li>

<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20150210192721/https://java.net/projects/open-jbi-components/sources/svn/show/trunk/contrib-other/camelse">camelse</a></li>

<li><a rel="nofollow" class="external text" href="http://logicoy.com/blogs/running-apache-camel-in-openesb/">Running Apache Camel in OpenESB</a></li>

<li><a rel="nofollow" class="external text" href="http://drdobbs.com/201202701">Introduction to programming for SCA</a> Dr. Dobb's</li>

<li><a rel="nofollow" class="external text" href="https://tuscany.apache.org/">Apache Tuscany – Open Source implementation of the SCA specification</a></li>

<li><a rel="nofollow" class="external text" href="http://download.oracle.com/docs/cd/E18050_01/salt/docs11gr1/index.html">SALT - Enterprise ready SCA runtime for C++, Python, Ruby, and PHP</a></li>

<li><a rel="nofollow" class="external text" href="http://www.pocomatic.com/docs/whitepapers/webservices/#sca-as-a-dsm">PocoCapsule for WS and SCA</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20071119030902/http://www.pocomatic.com/docs/whitepapers/webservices/#sca-as-a-dsm">Archived</a> 2007-11-19 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a> An open source C++ SCA container based on inversion-of-control (IoC) and domain-specific-modeling (DSM)</li>

<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20060612205504/http://www.codecauldron.org/">Newton open source distributed SCA & OSGi runtime</a></li>

<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20130109022529/http://wiki.ow2.org/frascati/Wiki.jsp?page=FraSCAti">A French public research project, which includes a SCA runtime called FraSCati</a></li>

<li><a rel="nofollow" class="external text" href="http://www.oasis-opencsa.org/sca">SCA Home Page at OASIS web site</a></li>

<li><a rel="nofollow" class="external text" href="http://www.oasis-opencsa.org/resources">Current SCA Resources & Collateral</a></li>

<li><a rel="nofollow" class="external text" href="http://www.osoa.org/display/Main/News+about+SCA+and+SDO">Latest SCA & SDO News</a></li>

<li><a rel="nofollow" class="external text" href="http://www.davidchappell.com/writing/Introducing_SCA.pdf">Introducing SCA – A tutorial by David Chappell, Chappell & Associates</a></li>

<li><a rel="nofollow" class="external text" href="http://www.eclipse.org/stp/sca/index.php">Eclipse STP/SCA sub project</a> An Open Source Eclipse project that provides a set of tools for SCA</li>

<li><a rel="nofollow" class="external text" href="http://microservices.io/index.html">Microservice architecture patterns and best practices</a></li>

<li><a rel="nofollow" class="external text" href="http://martinfowler.com/articles/microservices.html">martinfowler microservice architecture site</a></li>

<li><a rel="nofollow" class="external text" href="http://martinfowler.com/articles/microservices.html#SmartEndpointsAndDumbPipes">Smart endpoints and dumb pipes – martinfowler</a></li></ul></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2024-01-22" href="https://en.wikipedia.org/wiki/?title=Service_Component_Architecture&oldid=1197881958">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>